The CA API Gateway providing user access control intermediary services must generate audit records when successful/unsuccessful logon attempts occur.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-71469	CAGW-GW-000860	SV-86093r1_rule		Medium

Description
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). This requirement applies to the ALG traffic management functions, such as content filtering or intermediary services. This does not apply to audit logs generated on behalf of the device (device management). The CA API Gateway by default audits when unsuccessful attempts to log on to a Registered Service or the Gateway occur. To enable the auditing of successful events, the log level on the Gateway must be increased to INFO, as by default it is set to WARNING, which only audits events that may be considered an issue.

Description

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). This requirement applies to the ALG traffic management functions, such as content filtering or intermediary services. This does not apply to audit logs generated on behalf of the device (device management). The CA API Gateway by default audits when unsuccessful attempts to log on to a Registered Service or the Gateway occur. To enable the auditing of successful events, the log level on the Gateway must be increased to INFO, as by default it is set to WARNING, which only audits events that may be considered an issue.

STIG	Date
CA API Gateway ALG Security Technical Implementation Guide	2017-04-07

Details

Check Text ( C-71859r1_chk )
Open the CA API Gateway - Policy Manager. Locate the Global Policy created for "message-received". Open the policy and verify the "Audit Messages in Policy" Assertion has been added. If the Global policy does not exist or the "Audit Messages in Policy" Assertion is not present, this is a finding.

Fix Text (F-77789r1_fix)
Open the CA API Gateway - Policy Manager. If a Global Policy is not set for the system, create one by selecting "Tasks" from the main menu and choosing "Create Policy". Give the policy a name and select "Global Policy Fragment" from the Policy Type drop-down menu. Select "message-received" from the Policy Tag drop-down menu and click "OK". Locate the Global Policy created for "message-received". Open the policy and add the "Audit Messages in Policy" Assertion. Set the Level to "WARNING" to verify the normally successful logons are recorded as WARNINGS and not INFO.

Fix Text (F-77789r1_fix)

Open the CA API Gateway - Policy Manager.

If a Global Policy is not set for the system, create one by selecting "Tasks" from the main menu and choosing "Create Policy".

Give the policy a name and select "Global Policy Fragment" from the Policy Type drop-down menu.

Select "message-received" from the Policy Tag drop-down menu and click "OK".

Locate the Global Policy created for "message-received". Open the policy and add the "Audit Messages in Policy" Assertion. Set the Level to "WARNING" to verify the normally successful logons are recorded as WARNINGS and not INFO.